feat(tunnel): add configuration hot reload support #1582
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add support for hot reloading configuration without restarting cloudflared. This enables updating ingress rules, warp-routing settings, and origin request configuration on the fly.
Related issues: #240, #301, #512, #965
Changes
LocalConfigWatchercomponent that monitors config.yaml for changes via fsnotifyOrchestrator.UpdateConfig()mechanism (already used for remote-managed tunnels)Usage
What can be hot-reloaded
ingressruleswarp-routingoriginRequesttunnelUUIDcredentials-fileprotocolLimitations
Test plan
TestConvertLocalConfigToJSON*)TestValidateLocalConfig*)TestLocalConfigWatcher*)TestSignalShutdown)